Release Notes for Server SDK - Java.

Seclore 3.31.3.0 
Server SDK - Java 4.4.19.0
Feb 01, 2025

1) Bug fixes and upgrades. (ETM – 1798)   
    
-----------------------------------

Seclore 3.29.0.0 
Server SDK - Java 4.4.18.0
Sept 01, 2024

1) Added support for protecting interoperable design file formats (step, stp, dwg, dxf, igs, iges, jt, and x_t). (#17266) 
2) Other fixes. (#17820) 
    
-----------------------------------


Seclore 3.28.2.0 
Server SDK - Java 4.4.17.0
Apr 01, 2024

1) Added a method to generate an unwrapped Smail from the protected mail body. (#16729) 
        a. This unwrapped Smail is required for uploading the protected mail body to the ‘View Email’ link introduced in One-click Email Access feature. 
2) Other fixes and upgrades. (#16657, #16774, #16843, #16866) 
    
-----------------------------------

Seclore 3.28.0.0 
Server SDK - Java 4.4.16.0
Feb 01, 2024

1) Added some APIs to enable Server SDK enhancements. (#16252) 
    
-----------------------------------

Seclore 3.27.8.0 
Server SDK - Java 4.4.15.0
Oct 01, 2023

1) Updated the HTML buffer file templates. (#15202)
        a. When more than ten attachments were added to a protected email, unprotected copies of some of the attachments were sent to the recipient.   
        b. This issue was fixed by updating the header tags in the buffer file template. 
    
-----------------------------------

Seclore 3.27.4.0
Server SDK - Java 4.4.13.0
Jul 01, 2023

1) Seclore will now add an x-header to emails that’ll help applications detect whether an email was protected manually or via Email Auto Protector. (#14739)
       a. Further, the x-header will be retained even when a recipient replies to the email using Secure Email Viewer.
2) Buffer file updated with well-defined steps to help users open Seclore-protected files in mobile devices. (#14664)
3) Fixed the issue where files with long location paths wouldn’t get unprotected. (#14152) 
4) Other fixes. (#14738, #14707, #14645, #14406) 

----------------------------------

Seclore 3.25.0.0
Server SDK - Java 4.4.12.0
Oct 01, 2022

1) Updated the instructions in the buffer file for opening protected emails from the new version of the Outlook mobile app for Android. (#13531) 
       a. In the new version of the Outlook mobile app, users need to click the ellipsis, click ‘Open with’, and select Seclore to open protected emails. 

----------------------------------

Seclore 3.23.1.0
Server SDK - Java 4.4.11.0
May 01, 2022

1) Added support for Canadian French. (#12778)
2) Other fixes. (#12770, #11706) 

----------------------------------

Seclore 3.22.0.0
Server SDK - Java 4.4.10.0
Feb 16, 2022

1) Added HTML buffer files for Brazilian-Portuguese. (#12473)
2) Apache Log4j upgraded to version 2.17.1. (#12580)

----------------------------------
Seclore 3.21.0.0
Server SDK - Java 4.4.9.0
Jan 1, 2022

1) Apache Log4j upgraded to version 2.16.0. (#12201)
2) Other fixes. (#12082)

----------------------------------
Seclore 3.20.1.0
Server SDK - Java 4.4.8.0
Nov 1, 2021

1. Update the translated HTML buffer files Made changes to the native buffer file. (#10521)     

----------------------------------
Seclore 3.18.0.0
Server SDK - Java 4.4.7.0
Apr 1, 2021

1. Made changes to the native buffer file. (#10590) 
    a. In some cases, users see the Seclore’s buffer file when they open a protected file on their desktop. The buffer file contains the enterprise’s logo and a customized URL of a webpage that helps users with ways to open the protected file. 
    b. To enable faster deployment of the Policy Server for new Seclore customers, we’ve removed the enterprise logo from the buffer file and added a generic URL of a file opening app that will help users open the protected file. 
    c. Buffer files for existing Seclore customers will remain unaffected.  

2. Other fixes. (#10565)

----------------------------------
Seclore 3.17.0.0
Server SDK - Java 4.4.6.0
Mar 1, 2021

1. Fixed the issue where IBM JDK wouldn’t work with Seclore Server SDK - Java. (#10559)

----------------------------------
Seclore 3.16.5.0
Server SDK - Java 4.4.5.0
Feb 16, 2021

1. Users would now see an enhanced buffer page while opening a Seclore-protected file from a Microsoft Teams channel on Android devices. 
   This buffer page will guide users on ways to open protected files. (#10504)

----------------------------------

Seclore 3.16.4.0
Server SDK - Java 4.4.4.0
Feb 1, 2021

1. Fixed the issue where Seclore-protected files wouldn’t get HTML-wrapped with Server SDK - Java 4.4.3.0. (#10375)

----------------------------------

Seclore 3.15.0.0
Server SDK - Java 4.4.3.0
Oct 1, 2020

   1) Added support to retain classification metadata within HTML buffer files for discovery solutions like DLPs to read. (#9644)
   2) Added support for Mac Operating System. (#8907)
        a. Enterprises and integrating partners can now build integrations using Seclore Server SDK – Java on Mac OS.  
       
----------------------------------

Seclore 3.14.0.0
Server SDK - Java 4.4.2.0
August 1, 2020

    1) Updated HTML buffer file to display user instructions in raw HTML content. This is useful in scenarios where Seclore Protected file is opened in a 3rd party application that cannot render HTML content. (#9543, #9520) 
    2) Other fixes. (#9392) 
       
----------------------------------

Seclore 3.13.0.0
Server SDK - Java 4.4.1.0
Jun 1, 2020

    1) Fixed the issue where in certain cases an error message was displayed when an HTML wrapped file was opened in a browser. (#9227) 
        a. Before the fix: When a HTML wrapped protected file was opened in a browser, an error message was displayed instead of the buffer file due to delay in response from the Policy Server. 
        b. After the fix: While opening a HTML wrapped protected file in the browser, the buffer file is successfully displayed without any error.
 
       
----------------------------------

Seclore 3.11.0.0
Server SDK - Java 4.4.0.0
Feb 1, 2020

    1) Fixed the issue where email was sent with unprotected attachments when HTML wrap feature was disabled in the Policy Server and email body protection was enabled in Email Auto Protector rules. (#8644) 
       a. Before the change: When an email with attachments were protected and sent with the HTML wrap feature disabled in the Policy Server and email body protection enabled in Email Auto Protector ruled, the email was sent but with the attachments unprotected. 
       b. After the change: The email is sent in such a scenario with the email body unprotected and the attachments protected but unwrapped. 
    2) Introducing support for Universal Protection where non-standard file formats will be protected using full control rights and HTML wrapped for added security. (#8583)  
    3) Support for updated HTML buffer files. (#8441) 
    4) Other fixes. (#8170) 
       
----------------------------------
Seclore 3.10.15.0
Server SDK - Java 4.3.4.0
December 1, 2019

    1. Updated HTML Buffer Files (#8438)

----------------------------------
Seclore 3.10.14.0
Server SDK - Java 4.3.3.0
October 15, 2019

    1. Other fixes. (#8251)

----------------------------------
Seclore 3.10.13.0
Server SDK - Java 4.3.2.0
September 1, 2019

    1. Added support for the new HTML Wrapper pages.(#8093)

----------------------------------
Seclore 3.10.11.0
Server SDK - Java 4.3.1.0
August 1, 2019

    1) Configuration to make "Federal Information Processing Standards (FIPS)" optional. (#7975)
    2) Other fixes. (#7981)

----------------------------------
Seclore 3.10.9.0
Server SDK - Java 4.3.0.0
July 1, 2019

    1) Added Multilingual support. (#7684)

----------------------------------
Seclore 3.10.0.0
Server SDK - Java 4.2.1.0
March 1, 2019

    1) Optimized the memory consumption by reading data in chunksImproved performance by optimizing system memory utilization. (#7616)
    2) Other fixes. (#7613, #7614, #7615, #7623)

----------------------------------
Seclore 3.9.0.0
Server SDK - Java 4.2.0.0
Oct 1, 2018

    1. Added APIs to protect and unprotect a mails.
        a. The following new APIs are added to FSHelper. 
            1. protectMailBody(): Protects mail.
            2. unprotectMailBody(): Unprotects mail.
    2. All APIs can handle files of practically unlimited size. 
    3. Added API to get the Seclore File ID of an HTML wrapped file, getHTMLWrappedFileId().

----------------------------------
FileSecure 3.8.0.0
Server SDK - Java 4.1.0.0
Jun 12, 2018

    1. Added support to protect any file using basic protection.
        a. The following new APIs have been added to FSHelper. 
            1. isBasicProtectionSupported(): Checks whether the file is supported for Basic Protection.
            2. protectFileWithBasicProtection(): Protects file using Basic Protection.
            3. unprotectFileWithBasicProtection(): Unprotects file which has been protected with Basic Protection.

----------------------------------
FileSecure 3.6.3.0
Server SDK - Java 4.0.0.0
Mar 19, 2018

    1. Added support to use multiple Policy Servers simultaneously. (#6606)
        a. The following new APIs have been added to FSHelperLibrary. 
            1. initializeHelper(): Creates a new FSHelper object with new Policy Server session.
            2. getHelper(): Gets the FSHelper object and Policy Server session for given unique identifier.
            3. terminateHelper(): Terminates the FSHelper object and Policy Server session for given unique identifier.
        b. The following APIs are member methods of FSHelper object:
            1. isProtectedFile()
            2. isSupportedFile()
            3. protectX()
            4. unprotectX()
            5. sendRequest()
            6. wrap()
            7. unwrap() 
            8. isHTMLWrapSupported()
            9. isHTMLWrapped()
            10. getFileId()
            11. getFileHeader()
        c. This version is not backward compatible hence cannot be used without changing the application which is using Server SDK - Java 3.x.x.x or older.

    2. Added support to use AES CBC for content encryption.
    
    3. Changed file read and write chunk size to 4MB from 4KB during file protection and unprotection.
    
------------------------------
FileSecure 3.6.2.0
Server SDK - Java 3.0.2.0
Mar 16, 2018

    1. Added custom attribute in html wrapped file. (#6322)
        Note: This change is available in Inner layer (WSClient/HtmlWrapper) only, not available for public integration.
    
------------------------------ 
FileSecure 3.6.0.0
Server SDK - Java 3.0.1.0
Feb 1, 2018

    1. Upgraded SDK to use FIPS certified BouncyCastle library for encryption of file contents.
    
Notes : 
 - Support for Java 5 and 6 has been deprecated
 - BouncyCastle-FIPS cannot be used in the same JVM as the regular Bouncy Castle provider. The classes in the two jar files do not get along. If the application is already using BouncyCastle library then this SDK can not be used along with. 

------------------------------ 
### From the 'Server SDK - Java 3.0.0.0' release, Seclore API libraries for Java, .NET, and C/C++ will be released as separate releases ###
------------------------------
FileSecure 3.4.0.0
Server SDK - Java 3.0.0.0
Nov 1, 2017

   1. Added support for HTML wrapping. (#5575, #5577)
      a. The following new APIs have been added or updated accordingly. 
         a. wrap() : Wraps the requested protected document in HTML format (new). 
         b. unwrap() : Unwraps the requested wrapped document (new).  
         c. isHTMLWrapSupported() : Returns True if HTML wrapping is supported for the format of the requested document (new). 
         d. isHTMLWrapped() : Returns True if the requested document is HTML wrapped (new).  
         e. getFileId() : Updated to accept an HTML-wrapped document as input and return its File ID.
         f. getFileHeader() : Updated to accept an HTML-wrapped document as input and return its header.
      b. Requires Seclore Policy Server 3.0.1.0 or above.

   2. Optimized the protection and unprotection process. (#5575)
      a. ProtectX() and UnprotectX(): To optimize memory consumption, instead of loading the entire document into memory, it is divided into chunks and each chunk is read, protected/unprotected, and then written to disk individually. 

   3. Enabled two-factor authentication for communication between Policy Server and any integrated Enterprise Application. (#5774)
      a. Requires Policy Server 2.51.0.0 or above

   4. Enabled integrated applications to be assigned certain advanced privileges - such as unprotecting all files protected by that Policy Server. (#5774)
      a. Requires Policy Server 2.51.0.0 or above

   5. Strengthened internal product security for client-server communication with an additional encryption layer within the SSL tunnel. (#5774)
      a. Requires Policy Server 2.51.0.0 or above

   6. Changed relevant API(s) to reflect the new maximum document size limit allowed for protection: 1.8 GB. (#5774)

   7. Other fixes and enhancements. (#5774)

------------------------------
FileSecure 2.106.3.0
Web Service Client Library 1.12.1.0
Mar 1, 2017
 
   1. Added support for protecting files with .rh and .vds extensions for SAP 3D Visual Enterprise Viewer (versions 8 and 9). (#5351)
   2. Fixed the issue where protecting a file did not work as expected if Classification description was longer than 1000 characters. (#5322)
   3. Other fixes. (#5266, #5267, #5269, #5270, #5298, #5323, #5349, #5272, #5273)
  
------------------------------
FileSecure 2.99.0.0
Web Service Client Library 1.12.0.0
Sept 16, 2016

Enhancements:
   1. Enabled two-factor authentication for Enterprise Application integration. (#4828)
   2. Enabled integrated applications to be assigned certain advanced privileges - such as unprotecting all files protected by that Policy Server. (#4828)
   3. Strengthened internal product security for client-server communication with an additional encryption layer within the SSL tunnel. (#4828)
   
Note : Two-factor authentication, advanced privileges and secure communication requires Policy Server 2.51.0.0 FileSecure 2.96.0.0 or above. All three features have been implemented in .NET FSHelper library.
  
------------------------------
FileSecure 2.97.0.0
Web Service Client Library 1.11.3.0
Aug 15, 2016

Bug Fixes:
   1. Enhanced internal product security by making various cryptographic functions consistent with other product components. (#4874)

------------------------------
FileSecure 2.89.0.0
Web Service Client Library 1.11.2.0
Mar 03, 2016

Enhancements:
   1. .NET APIs to manipulate transient format. (#4514)
      a. Transient format is generated by FileSecure Lite for Windows. Transient format applies to following file formats: docx, docm, xlsx, xlsm, xlsb, pptx, pptm.
      b. bool IsTransientFile(string): Returns whether file is in transient format or not.
      c. bool IsTransientFile(ILockBytes): Returns whether file is in transient format or not.
      d. void ConvertFromTransient(string): Converts transient format into FileSecure format.
      e. These APIs are avaliable on .NET platform only.

------------------------------
FileSecure 2.67.0.0
Web Service Client Library 1.11.1.0
Nov 24, 2014

Bug fixes: 
   1. Issue: Files protected from .NET library does not open or unprotect if Policy Server identifier has '&', '<', '>', '"' or ''' (XML special characters). (#3606)
      Resolution: .NET library has been changed to take care of this issue.
   2. Issue: Cannot connect to Policy Server even if Policy Server is deployed with valid SSL certificate when is-production flag is set TRUE in configuration. (#3607)
      Resolution: .NET library has been changed to take care of this issue.
   3. Issue: Documentation is not in user-friendly format. (#3608)
      Resolution: Documentation is available in .CHM format rather than .XML format.
   4. Issue: Required to compile the software which use .NET library because of strong name signing. (#3621)
      Resolution: Publisher policy assembly library is distributed with package.
 
------------------------------
FileSecure 2.61.0.0
Web Service Client Library 1.11.0.0
May 28, 2014

Features:
   1. Pure .NET interface for easy integration with .NET applications. (#2632): 
      - Following APIs are provided:
         - IsProtectedFile()
         - IsProtectedFile()
         - IsSupportedFile()
         - ProtectX()
         - UnprotectX()
         - SendRequest()
         - Initialize()
         - Terminate()
      - This APIs require .NET framework 2.0 of higher.

------------------------------
FileSecure 2.53.0.0
Web Service Client Library 1.10.0.0
Dec 6, 2013

Features:
   1. .NET interface for easy integration with .NET applications. (#2682): 
      - Following APIs are provided:
         - bool IsProtectedFile(string)
         - bool IsProtectedFile(byte[])
         - bool IsSupportedFile(string)
         - string Protect(string, ProtectionType, string, string, string)
         - void Unprotect(string, string)
         - string SendRequest(RequestType, string)
         - void Initialize(string, string)
         - void Terminate()
   2. Display path for file being protected/unprotected (#2862): In situations where temporary file needs be created with random name to protect/unprotect content, temporary file name is recorded in activity logs in Policy Server. This makes difficult to search protected files and activities based on file name. Java APIs are changed to accept display name for such file which is send to Policy Server and can be used in search. There are two new APIs (protectEx and unprotectEx) are provided which accepts display name for file being protected or unprotected. This APIs are available in Java only.

Bug fixes: 
   1. Java APIs in WebLogic Server throws java.lang.ClassCastException (#2899): Java APIs cannot be used in WebLogic because WebLogic provides different implementation of HttpURLConnection interface which Java APIs are not expecting (Java APIs are expecting java.net.ssl.HttpsURLConnection while default implementation in WebLogic is weblogic.net.http.SOAPHttpsURLConnection). Java APIs will take care of such scenario.
   2. Proxy port is skipped by C APIs in configuration (#2684): Proxy port provided in configuration file is skipped by C APIs and C APIs are not able to connect Policy Server if proxy is required. This is applicable to C APIs only. However, proxy port can be appended to proxy server value separated ‘:’ in the configuration as a workaround. C APIs now reads proxy port from appropriate place from configuration and use the same. It also takes care to use proxy port provided in proxy server value if proxy port is appended to proxy server as workaround.

Notes:
   1. Web Service API documentation and Sample Code is deprecated: Sample Code and API documentation for old version of APIs (known as Web Service APIs) are deprecated. Customers are expected to migrate to new APIs which are easy to use.

------------------------------
FileSecure 2.38.0.0
Web Service Client Library 1.9.0.0
Sept 26, 2012

Features:
   1. A new simplified library, built on top of web services of FileSecure Policy Server has been provided in this release. It provides easy interface primarily to protect or unprotect files. This library internally takes care of connection with Policy Server by maintaining a connection pool. For details, please refer the documentation provided along with.
   * This library currently supports protection with HotFolder only.
   * Java APIs are provided in this version.

Bug fixes: 
   1. OpenOffice 2.4.3 shows warning to upgrade OpenOffice if file protected using WS Client Library is opened in OpenOffice 2.4.3. (#1686)
   
------------------------------
FileSecure 2.36.0.0
Web Service Client Library 1.8.0.0
Aug 27, 2012

Features:
   1. A new simplified library, built on top of web services of FileSecure Policy Server has been provided in this release. It provides easy interface primarily to protect or unprotect files. This library internally takes care of connection with Policy Server by maintaining a connection pool. For details, please refer the documentation provided along with. (#1598)
   * This library currently supports protection with HotFolder only.
   * Only C APIs are provided in this version.
   
------------------------------
FileSecure 2.33.1.0
Web Service Client Library 1.7.1.0
May 24, 2012

Features:
   1. Provision to protect a File using external reference identifier of Hot Folder and File.
   
Bug fixes: 
   1. Explicit call to Garbage Collector after processing large files in Java Library.
   2. IInitializeW/A() crashes randomly in C Library.
   
------------------------------
FileSecure 2.33.0.0
Web Service Client Library 1.7.0.0
May 11, 2012

Features:
   1. Provide implementation for connection pool to connect with PS. Also provided implementation in sample code to use the connection pool. (#1452)
   
Bug fixes: 
   1. Remove Digest validation of file contents during unprotect.
   2. Application may hang while protecting large file especially when sufficient disk space is not available or file is placed on remote folder.
   
------------------------------
FileSecure 2.32.0.0
Web Service Client Library 1.6.0.0
Jan 24, 2012

Features:
   1. Support for buffer file of size upto 1020K in java library. (#799)
   
Bug fixes: 
    1. HttpServletResponse was read without passing the "UTF-16LE" encoding in the sample code.
   2. File protected with buffer file of size 60K, 124K, 252K, 508K, 1020K are treated as corrupted (#1213)
   3. Sample Code (C) crashes if executed on Windows 7.

------------------------------
FileSecure 2.29.0.0
Web Service Client Library 1.5.0.0
Aug 19, 2011

Features:
    1. Provided x64 version of C library.

------------------------------
FileSecure 2.28.0.0
Web Service Client Library 1.4.0.0
July 27, 2011

Features:
   1. Added IProtectExW/A API in Win32 Library which accepts request type, as an additional parameter. (Refer documentation for details)
   2. Added IGetFileInfoExW/A API in Win32 Library which accepts display path of the file, as an additional optional parameter. (Refer documentation for details)
   3. Added IGetFileHeaderXMLFromByteW/A API in Win32 Library which returns file header from BYTE array. (Refer documentation for details)
   4. Added IIsProtectedW/A API in Win32 Library which returns whether file is protected or not using file path.
   5. Added IIsProtectedFromByte API in Win32 Library which returns whether file is protected or not using BYTE array containing file content.
   6. Added ILogInfoVW/A, ILogErrorVW/A and ILogDebugVW/A APIs in Win32 Library which accept va_list.
   7. Support for buffer file of size upto 1020K in Win32 Library. (#799)
   8. Support to use response of Protect With External Reference Identifier assigned to Hot Folder and File for protecting file using IProtectExW/A API.

Bug Fixes:
   1. Sample Code crashes if Policy Server returns response larger than 8000 characters.

------------------------------
FileSecure 2.20.0.0
Web Service Client Library 1.3.0.0
Sep 03, 2010

Features:
    1. Added new request type constant for 'protect with default protection details'.
        
Bug fixes: 
    1. Error in padding logic of WSClient Library logic while calculating the file data in the java library.(#582)
    2. The select owner pop-up on the HotFolder integration page, does not continue the user session.(#410)

------------------------------
FileSecure 2.17.0.0
Web Service Client Library 1.2.0.0
Feb 05, 2010

    Features:
    
    1. Added constants for request types for each request exposed as Web Services.
    2. Added new Sample code to authenticate HotFolderCabinet.
    3. Changed existing samples to access the common URL exposed by Policy Server, for Web Services request.
    4. Changed existing samples to send new XML structure in request. 

------------------------------
FileSecure 2.13.0.0
Web Service Client Library 1.1.0.0
Oct 23, 2009

    Features:
    
    1. Provided C Client Library for Web Services Interface.
    2. Extracted Java Library Guide from 'FileSecure Web Services Interface.pdf' 
        and created separate document called 'FileSecure Web Services Java Client Library Guide.pdf'. 
        Provided similar document for C Client Library.
    
------------------------------
FileSecure 2.12.0.0
Web Service Client Library 1.0.0.0
Sept 30, 2009

    This is the first release of the Web Service Client Library. This library 
    provides methods and API to protect, unprotect files and the communication 
    mechanism between the client and the Policy Server Web Service. 
